RENODE <cover>
 
renumbers nodes for coverage arcs and updates values for FNODE# and
TNODE# in the AAT when it exists.
 
argument
 
<cover> - the coverage whose nodes will be renumbered.
 
notes
 
feature attribute tables as well as polygon and arc topology are
maintained by RENODE.
 
RENODE updates the arc-node topology by renumbering the from-nodes and
to-nodes of each arc, and identifying arcs which share the same node
locations.  RENODE renumbers the internal node numbers for each arc,
assigns the same node number for arcs which share a common node
location, and updates the FNODE# and TNODE# items in the AAT when it
exists.
 
If an NAT is present, RENODE is identical to a BUILD with the NODE
option.
 
All nodes in the coverage are sequentially renumbered starting with 1.
 
The coordinate precision of the coverage is unaffected by RENODE.
 
 
discussion
 
There are many ARC/INFO commands which do not establish or reset
internal node numbers.  For example, GENERATE does not set  internal
node numbers; they have a value of 0 for new arcs created in GENERATE.
RESELECT, ELIMINATE and DISSOLVE will keep the existing internal node
numbers of the input coverage.  BUILD with LINE will not correct these
situations.  BUILD with POLY, MATCHNODE and CLEAN will also renumber
nodes in addition to their other operations.  Thus, RENODE is a fast,
efficient method to renumber nodes.
 
It is desirable for the internal numbers of all nodes to be sequentially
numbered and to have nonzero values.  Also, if two or more nodes occur
at the same x,y location, they should be identified by the same internal
node numbers.  These conditions are important for using some other ARC/INFO
operations.
 
To list and plot node errors, ARC and ARCPLOT look for different node
numbers on arcs.  If only two arcs share the same internal node number,
the node is identified as a pseudo node.  If only one arc has the
internal node number, the node is identified as a dangling node.  Thus,
connecting arcs should share the same node number.  Otherwise, node
error verification and correction can be more difficult.
 
The NETWORK programs ROUTE and ALLOCATE use the internal node numbers to
define the connectivity of arcs in a network.  Arcs which have a common
from-node or to-node number are assumed to be connected to each other.
 
Before creating a DLG file using the ARCDLG, each node should be
sequentially numbered using RENODE.
 